Rollup of 5 pull requests - #161347
Conversation
Signed-off-by: Aland <158173939+aland-omed@users.noreply.github.com>
- Update a link to MCU list in the code and make it an actual link - Make avr-tester link point to the crate page (which is more expected and informative) instead of a repository (which has also moved)
`./x` was duplicated; the explanation of when to use alternatives was not quite correct; and the intro sentence was also slightly inaccurate.
Give better examples of how to run `x`
fix some typos and update some links
This makes it easy for us to see as maintainers what needs an owner, and helps people reading the guide a little bit so they don't get excited then disappointed.
…ir-macro-docs Add documentation for some `rustc_type_ir` macros
Explicitly mark stub chapters in the table of contents
- delete `inline-asm` and redirect it to `asm` - rename `optional-x86_64-gnu-parallel-frontend` to include the `optional-`, matching rl/r - add a redirect from `/llm-guidance/` to `/llm-guidance`, i think there's some docs floating around that accidentally suggest the former.
Fix orphaned chapters
- Remove duplicate "chicken-and-egg" explanation. It only needs to be in one place. - Change most references from `x.py` to `./x`, "bootstrap", or `bootstrap.py` as appropriate. Keep the ones where `x.py` is load-bearing. - Remove over-long and duplicated instructions around the bootstrap wrappers
Cleanup bootstrap references
Update offload docs for macro and third pass
This updates the rust-version file to 2c39ff4.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@2c39ff4 Filtered ref: rust-lang/rustc-dev-guide@52b5831 Upstream diff: rust-lang/rust@e64c8a6...2c39ff4 This merge was created using https://github.com/rust-lang/josh-sync.
bump `mdbook-linkcheck2` in CI
Rustc pull update
md links work on both Github and in the published site, whereas html links only work on the published site. Update `mdbook-linkcheck2` to the latest version, which supports a new `require-md-extension` option; enable that option; then fix all the errors.
Use .md links consistently
Document debuginfo `repr` directive
…ce-folder-2473 docs: Clarify Neovim workspace path setup
Add a hint about unflatten and an internal link to MIR outlives graphs to advertise them better.
…malized-ty-return, r=khyperia Make const eval return normalized ty closes: rust-lang/trait-system-refactor-initiative#286 closes: rust-lang#156294 r? @lcnr
…h726 Fix a couple of links in AVR target documentation - Update a link to MCU list in the code and make it an actual link - Make avr-tester link point to the crate page (which is more expected and informative) instead of a repository (which has also moved)
…anitizers, r=mu001999 compiler: Account for default_sanitizers when comparing target modifiers Prior to this PR, rustc would complain about mismatched ABIs if crates built with -Zsanitizer=shadow-call-stack were mixed with crates not built with -Zsanitizer=shadow-call-stack for the exact same target where SCS is one of the default_sanitizers. Rustc should also take into account default_sanitizers before doing the target modifiers checks. AI: Gemini was used to initially help write tests for this PR. I edited some of it and reviewed it to the best of my ability before submitting.
rustc-dev-guide subtree update Subtree update of `rustc-dev-guide` to rust-lang/rustc-dev-guide@5613bfe. Created using https://github.com/rust-lang/josh-sync. r? @ghost
|
@bors r+ p=5 |
This comment has been minimized.
This comment has been minimized.
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 407371f (parent) -> f7d782a (this PR) Test differencesShow 36 test diffsStage 1
Stage 2
Additionally, 11 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard f7d782a3be46d6bb4b9792fe69a61db389ba1769 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (f7d782a): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary 3.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis perf run didn't have relevant results for this metric. Binary sizeResults (primary -0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 458.213s -> 456.256s (-0.43%) |
|
📌 Perf builds for each rolled up PR:
parent commit: 407371fb75 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Successful merges:
binutilsbefore buildinggcc#161006 - GuillaumeGomez:gcc-binutils, r=Kobzol")r? @ghost
Create a similar rollup